Skip to content

Conversation

@camschaecisco
Copy link
Contributor

Description

Add support for EVPN instance profile configuration on VLANs, enabling both manual EVI and auto EVI with profile modes.

Changes

  • Add evpn_instance_protected mapping for manual EVI configuration
  • Add evpn_instance_profile mapping for auto EVI with profile support
  • Add evpn_instance_profile_protected mapping for auto EVI protected mode
  • Keep existing evpn_instance and evpn_instance_vni mappings (now use new provider YANG path)

Dependencies

Depends on Provider PR: CiscoDevNet/terraform-provider-iosxe#349

This PR requires the provider changes to be merged first, as it references new provider attributes.

Testing

  • ✅ Pre-commit hooks passed (terraform fmt, tflint, terraform-docs)
  • ✅ Local testing validated with manual EVI mode on Cat9k
  • ✅ Local testing validated with profile mode on Cat9k (after manual L2 profile creation)
  • ✅ Terraform plan/apply/destroy successful

YAML Configuration Example

Manual EVI Mode:

vlan:
  vlans:
    - id: 100
      evpn_instance: 100
      evpn_instance_vni: 10100
      evpn_instance_protected: true

Profile Mode (NEW FEATURE):

vlan:
  vlans:
    - id: 100
      evpn_instance_profile: MY_EVPN_PROFILE
      evpn_instance_profile_protected: true

Breaking Change Migration

The module maintains backward compatibility - users continue using the same YAML field names (evpn_instance, evpn_instance_vni), which now map to the new provider attributes that use the current YANG path.

- Add evpn_instance_protected mapping for manual EVI configuration
- Add evpn_instance_profile mapping for auto EVI with profile
- Add evpn_instance_profile_protected mapping for auto EVI protected mode
- Keep existing evpn_instance and evpn_instance_vni mappings (now point to new YANG path)

This enables users to configure 'member evpn-instance profile <name>' on VLANs
for IOS-XE >= 17.15.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants